Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0f5e6fe134b3355c764eb8d81f636e11e3138b51f22f3be8aa5c155f06d61ab

Tx prefix hash: 282438cafdb0d8a003294fb05bb0e674ddcb83a19f42edb67f57145a6ba83b39
Tx public key: efac35db52e94b2b502a69f864a4eff978366c5307040534c4d05a8e9d79dd0e
Timestamp: 1670520984 Timestamp [UCT]: 2022-12-08 17:36:24 Age [y:d:h:m:s]: 01:334:14:03:36
Block: 648240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 500136 RingCT/type: yes/0
Extra: 01efac35db52e94b2b502a69f864a4eff978366c5307040534c4d05a8e9d79dd0e0211000000017e406890000000000000000000

1 output(s) for total of 4.366281903000 dcy

stealth address amount amount idx
00: 74ce3b6a6feb8e4fe6e9c8c86ac50ba515ed871563059475ce422ae641c12007 4.366281903000 1088565 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": 648250, "vin": [ { "gen": { "height": 648240 } } ], "vout": [ { "amount": 4366281903, "target": { "key": "74ce3b6a6feb8e4fe6e9c8c86ac50ba515ed871563059475ce422ae641c12007" } } ], "extra": [ 1, 239, 172, 53, 219, 82, 233, 75, 43, 80, 42, 105, 248, 100, 164, 239, 249, 120, 54, 108, 83, 7, 4, 5, 52, 196, 208, 90, 142, 157, 121, 221, 14, 2, 17, 0, 0, 0, 1, 126, 64, 104, 144, 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