Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb338de7e8d2904055ef43ec9978e67a02f95f71a7a652cc15bf37a8844350cb

Tx prefix hash: f77c762c66e10b2a3d0453aa017d26ebb4ffe9e12a8a538d4cf26ef45390b70e
Tx public key: 927ef6acab89054a82ef4a5495a1b1e98d82a7bd1ad2a23fb57aa9af53cbaea2
Timestamp: 1647904409 Timestamp [UCT]: 2022-03-21 23:13:29 Age [y:d:h:m:s]: 02:281:14:41:34
Block: 463554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 720783 RingCT/type: yes/0
Extra: 01927ef6acab89054a82ef4a5495a1b1e98d82a7bd1ad2a23fb57aa9af53cbaea2021100000003bf7ee4e7000000000000000000

1 output(s) for total of 17.867073604000 dcy

stealth address amount amount idx
00: 54671dce2b1baa6160ff8e2f6b0edc9a1ca1d25a7bc266c08b78c6f247f7e13d 17.867073604000 881243 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": 463564, "vin": [ { "gen": { "height": 463554 } } ], "vout": [ { "amount": 17867073604, "target": { "key": "54671dce2b1baa6160ff8e2f6b0edc9a1ca1d25a7bc266c08b78c6f247f7e13d" } } ], "extra": [ 1, 146, 126, 246, 172, 171, 137, 5, 74, 130, 239, 74, 84, 149, 161, 177, 233, 141, 130, 167, 189, 26, 210, 162, 63, 181, 122, 169, 175, 83, 203, 174, 162, 2, 17, 0, 0, 0, 3, 191, 126, 228, 231, 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