Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84b44d8582f0803b8a4e19d3ca63864f74a8b3059b52a3b9d8c63423216c72f2

Tx prefix hash: b995445a72cbdf341d80d1b932f8beea85284167de5715a9e783df3ab8ac20f5
Tx public key: 81167ee33ae73c72db445c4223067b502acd7a5ee3d8f41cf42dcbdc69e34466
Timestamp: 1707636183 Timestamp [UCT]: 2024-02-11 07:23:03 Age [y:d:h:m:s]: 01:268:23:21:20
Block: 955040 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 450989 RingCT/type: yes/0
Extra: 0181167ee33ae73c72db445c4223067b502acd7a5ee3d8f41cf42dcbdc69e344660211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ed255fccdb1bde4b322cab44faec749776c2415c7160269c2d12e96b182f4f0 0.600000000000 1414322 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": 955050, "vin": [ { "gen": { "height": 955040 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ed255fccdb1bde4b322cab44faec749776c2415c7160269c2d12e96b182f4f0" } } ], "extra": [ 1, 129, 22, 126, 227, 58, 231, 60, 114, 219, 68, 92, 66, 35, 6, 123, 80, 42, 205, 122, 94, 227, 216, 244, 28, 244, 45, 203, 220, 105, 227, 68, 102, 2, 17, 0, 0, 0, 1, 0, 17, 5, 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