Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d6bd14259b9d163c2c8f4b19cb67f4a2461324231648ec8ef66d019b69fac7c

Tx prefix hash: 85a0ac7de9616c9b3c6589a74a3cfd51880340cf189e8efdf1f6a9f2eff334e4
Tx public key: 60af293df734e614405c543528d849a27941c4b8ed2db54567df11f0460b055a
Timestamp: 1697163219 Timestamp [UCT]: 2023-10-13 02:13:39 Age [y:d:h:m:s]: 02:025:03:42:00
Block: 868426 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 537586 RingCT/type: yes/0
Extra: 0160af293df734e614405c543528d849a27941c4b8ed2db54567df11f0460b055a0211000000024b8f5122000000000000000000

1 output(s) for total of 0.813849668000 dcy

stealth address amount amount idx
00: f20b8c27404234062de4bdf0ce2411ad5f2c850488d455e709908bc1cf5cde73 0.813849668000 1323233 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": 868436, "vin": [ { "gen": { "height": 868426 } } ], "vout": [ { "amount": 813849668, "target": { "key": "f20b8c27404234062de4bdf0ce2411ad5f2c850488d455e709908bc1cf5cde73" } } ], "extra": [ 1, 96, 175, 41, 61, 247, 52, 230, 20, 64, 92, 84, 53, 40, 216, 73, 162, 121, 65, 196, 184, 237, 45, 181, 69, 103, 223, 17, 240, 70, 11, 5, 90, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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