Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34e5f8f706ae0870a547ac4b52d721a7b547a58d57b89b48f739423c55b5795b

Tx prefix hash: 09c13e1f76505198783ed68c228d447ebe61efc481d25511dd944175afcda10b
Tx public key: 35cc7b6b1117c7e4a8624005ee560b7e5f90e71a3a059a337b6385240a7f7bd0
Timestamp: 1740685889 Timestamp [UCT]: 2025-02-27 19:51:29 Age [y:d:h:m:s]: 00:266:01:58:49
Block: 1228583 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187929 RingCT/type: yes/0
Extra: 0135cc7b6b1117c7e4a8624005ee560b7e5f90e71a3a059a337b6385240a7f7bd00211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db9a18331e875e33b71429a9f0af3efdd0ddf5c58595a04e8f1a0583d2acc5ff 0.600000000000 1715464 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": 1228593, "vin": [ { "gen": { "height": 1228583 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db9a18331e875e33b71429a9f0af3efdd0ddf5c58595a04e8f1a0583d2acc5ff" } } ], "extra": [ 1, 53, 204, 123, 107, 17, 23, 199, 228, 168, 98, 64, 5, 238, 86, 11, 126, 95, 144, 231, 26, 58, 5, 154, 51, 123, 99, 133, 36, 10, 127, 123, 208, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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