Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 48afb5c5ab6c38a034707c14e66cd7847d4761240cd74c16686d9691d2b723a0

Tx prefix hash: 4641b1e47abd1573f6f71fa5e056c5f6f60141ca20fa05bd92d20ff9cfd9a21e
Tx public key: 6098c576ea8955a8f23325b37316403d3a46d1a71d6d38af5c0f18fbc51a8ac5
Timestamp: 1633725123 Timestamp [UCT]: 2021-10-08 20:32:03 Age [y:d:h:m:s]: 03:124:08:41:07
Block: 349357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 865933 RingCT/type: yes/0
Extra: 016098c576ea8955a8f23325b37316403d3a46d1a71d6d38af5c0f18fbc51a8ac50211000000015d7cc334000000000000000000

1 output(s) for total of 42.700765221000 dcy

stealth address amount amount idx
00: 539ef350db1d0747d073c8f8018c69168ae0a9681739aea9d6d53f39f43cdbc6 42.700765221000 715288 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 349367, "vin": [ { "gen": { "height": 349357 } } ], "vout": [ { "amount": 42700765221, "target": { "key": "539ef350db1d0747d073c8f8018c69168ae0a9681739aea9d6d53f39f43cdbc6" } } ], "extra": [ 1, 96, 152, 197, 118, 234, 137, 85, 168, 242, 51, 37, 179, 115, 22, 64, 61, 58, 70, 209, 167, 29, 109, 56, 175, 92, 15, 24, 251, 197, 26, 138, 197, 2, 17, 0, 0, 0, 1, 93, 124, 195, 52, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8