Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0347d587d436ab2141ca9d25a3e0726b1c7a824475d6a27a8e2aa55c0c637378

Tx prefix hash: bb941a7362f9e4ea89dbd94ab04d4a29fae3c1bed116fe8a4e973fb4dec1fe4a
Tx public key: 0cff0e1eb6dc59988bc333dcdf1a6aacd40f728dac310e14549889c347cfbf40
Timestamp: 1628862851 Timestamp [UCT]: 2021-08-13 13:54:11 Age [y:d:h:m:s]: 03:138:13:18:15
Block: 313209 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 872234 RingCT/type: yes/0
Extra: 010cff0e1eb6dc59988bc333dcdf1a6aacd40f728dac310e14549889c347cfbf4002110000001d58045e5b000000000000000000

1 output(s) for total of 56.261205683000 dcy

stealth address amount amount idx
00: c39076bec4ace6b9d68959839120089c02cf426e1f0f510809a896646fe50e84 56.261205683000 651772 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": 313219, "vin": [ { "gen": { "height": 313209 } } ], "vout": [ { "amount": 56261205683, "target": { "key": "c39076bec4ace6b9d68959839120089c02cf426e1f0f510809a896646fe50e84" } } ], "extra": [ 1, 12, 255, 14, 30, 182, 220, 89, 152, 139, 195, 51, 220, 223, 26, 106, 172, 212, 15, 114, 141, 172, 49, 14, 20, 84, 152, 137, 195, 71, 207, 191, 64, 2, 17, 0, 0, 0, 29, 88, 4, 94, 91, 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