Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 881d0c33d97ed041ce9d4b875ff1f3766d50cf4d9bc308d7dbfafa681dfa281c

Tx prefix hash: f7a51979bceb008a9f37689abf18aa71c6303601873fa73af1a9edab5cbd0f75
Tx public key: d37416cfc875f6f0607184924e43149bea2ed975565bf8ed4482fad6fea84a75
Timestamp: 1696937154 Timestamp [UCT]: 2023-10-10 11:25:54 Age [y:d:h:m:s]: 01:183:14:03:25
Block: 866564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 392236 RingCT/type: yes/0
Extra: 01d37416cfc875f6f0607184924e43149bea2ed975565bf8ed4482fad6fea84a7502110000000b75e3f0e9000000000000000000

1 output(s) for total of 0.825493718000 dcy

stealth address amount amount idx
00: 89efb0f0a8ec4c7cbf75c5cfbfc54f42d4d74bd6b5600e5822eb7806265588c9 0.825493718000 1321170 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": 866574, "vin": [ { "gen": { "height": 866564 } } ], "vout": [ { "amount": 825493718, "target": { "key": "89efb0f0a8ec4c7cbf75c5cfbfc54f42d4d74bd6b5600e5822eb7806265588c9" } } ], "extra": [ 1, 211, 116, 22, 207, 200, 117, 246, 240, 96, 113, 132, 146, 78, 67, 20, 155, 234, 46, 217, 117, 86, 91, 248, 237, 68, 130, 250, 214, 254, 168, 74, 117, 2, 17, 0, 0, 0, 11, 117, 227, 240, 233, 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