Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 372627a60d66fe171923096ff996c5776357a5eaf8db0affba9146a7b907ada5

Tx prefix hash: 05634283ad0aef7c6fd79b6dee73e1055a1b62d2d2099790cd5aa043b7ead638
Tx public key: 7b08d71521a23863e93878ec108f463ce5a1b2f4ef1dd11e282ccce0b0db1d72
Timestamp: 1709121112 Timestamp [UCT]: 2024-02-28 11:51:52 Age [y:d:h:m:s]: 01:057:17:06:53
Block: 967369 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302263 RingCT/type: yes/0
Extra: 017b08d71521a23863e93878ec108f463ce5a1b2f4ef1dd11e282ccce0b0db1d720211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 80df189d6afcb4d31aef821ce0828492ae59ea458f85e9430c8006970073f276 0.600000000000 1427146 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": 967379, "vin": [ { "gen": { "height": 967369 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80df189d6afcb4d31aef821ce0828492ae59ea458f85e9430c8006970073f276" } } ], "extra": [ 1, 123, 8, 215, 21, 33, 162, 56, 99, 233, 56, 120, 236, 16, 143, 70, 60, 229, 161, 178, 244, 239, 29, 209, 30, 40, 44, 204, 224, 176, 219, 29, 114, 2, 17, 0, 0, 0, 4, 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