Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7c73722c01b7f86b390c35032a09b00dd9a69b7d214c8e57d0621379091d491

Tx prefix hash: 37ebbebc3c88e8bc058685dd7ed7857c0a98eb9d96ee8f18bee86fa56a8c734f
Tx public key: dfd091ea20e2e8384dd7f5635374cbedcc3daf9c486c5025f6eb18c1c05b3d1c
Timestamp: 1707502549 Timestamp [UCT]: 2024-02-09 18:15:49 Age [y:d:h:m:s]: 01:057:04:55:25
Block: 953937 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301920 RingCT/type: yes/0
Extra: 01dfd091ea20e2e8384dd7f5635374cbedcc3daf9c486c5025f6eb18c1c05b3d1c0211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4bf35467d5991f3bf80870546bc2768b3155f72d2ed9bf3984bc4310eeeca68e 0.600000000000 1413209 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": 953947, "vin": [ { "gen": { "height": 953937 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4bf35467d5991f3bf80870546bc2768b3155f72d2ed9bf3984bc4310eeeca68e" } } ], "extra": [ 1, 223, 208, 145, 234, 32, 226, 232, 56, 77, 215, 245, 99, 83, 116, 203, 237, 204, 61, 175, 156, 72, 108, 80, 37, 246, 235, 24, 193, 192, 91, 61, 28, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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