Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c36fbe408e27f8c3137d9f1bb0c68d9cb46efc4748f8f3e51b8692fc5e3454b

Tx prefix hash: 371d96064d2ec30877499b105243c077ee5269c0b408d68ab634628bcf38d220
Tx public key: 081ccd2e44793c9650b96f48b3d31efb053d91d1396a2bd8b0ccee2e5951754f
Timestamp: 1704066329 Timestamp [UCT]: 2023-12-31 23:45:29 Age [y:d:h:m:s]: 01:096:20:02:49
Block: 925451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330312 RingCT/type: yes/0
Extra: 01081ccd2e44793c9650b96f48b3d31efb053d91d1396a2bd8b0ccee2e5951754f021100000002ac328d11000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3e3f4a0c1021c2ae56e4cfc3ceecfd42a5803fb8edb6b7ba647df6339c5af1d 0.600000000000 1383213 of 15

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": 925461, "vin": [ { "gen": { "height": 925451 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3e3f4a0c1021c2ae56e4cfc3ceecfd42a5803fb8edb6b7ba647df6339c5af1d" } } ], "extra": [ 1, 8, 28, 205, 46, 68, 121, 60, 150, 80, 185, 111, 72, 179, 211, 30, 251, 5, 61, 145, 209, 57, 106, 43, 216, 176, 204, 238, 46, 89, 81, 117, 79, 2, 17, 0, 0, 0, 2, 172, 50, 141, 17, 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