Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d967a1912fe3b10dabf8e227c387957f81159178726e6ad99f479afac83f30c9

Tx prefix hash: 847773cac1cc42d12487156444f3a8c8ff6894065105bf8e6e6459fcb7848f8a
Tx public key: f208f3e9f76991af213fbf7d841175e19d54ee63fd3b34f3378aa464bdb7ecbe
Timestamp: 1700873057 Timestamp [UCT]: 2023-11-25 00:44:17 Age [y:d:h:m:s]: 01:346:13:32:20
Block: 898987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 506556 RingCT/type: yes/0
Extra: 01f208f3e9f76991af213fbf7d841175e19d54ee63fd3b34f3378aa464bdb7ecbe0211000000014b8f5122000000000000000000

1 output(s) for total of 0.644588965000 dcy

stealth address amount amount idx
00: 39d471ad495670cc4f02d96eecbc2d103558ac8dcae7ce8d3d35b6d4ee167212 0.644588965000 1355424 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": 898997, "vin": [ { "gen": { "height": 898987 } } ], "vout": [ { "amount": 644588965, "target": { "key": "39d471ad495670cc4f02d96eecbc2d103558ac8dcae7ce8d3d35b6d4ee167212" } } ], "extra": [ 1, 242, 8, 243, 233, 247, 105, 145, 175, 33, 63, 191, 125, 132, 17, 117, 225, 157, 84, 238, 99, 253, 59, 52, 243, 55, 138, 164, 100, 189, 183, 236, 190, 2, 17, 0, 0, 0, 1, 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