Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2ec0fbf778572ff0df9a67038fed46b7c453d433bb82cbdcde4a9c8aedc6bbc

Tx prefix hash: e6d636032e8b928a81ea462a39cbe833832ffffcb7e6523fcae98860b32b4f79
Tx public key: 5cc33b0e49bf4fb42053d7c84e2a8feae33b8913636eefbfedf20843d5d92701
Timestamp: 1708314852 Timestamp [UCT]: 2024-02-19 03:54:12 Age [y:d:h:m:s]: 01:122:13:28:52
Block: 960679 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 348514 RingCT/type: yes/0
Extra: 015cc33b0e49bf4fb42053d7c84e2a8feae33b8913636eefbfedf20843d5d927010211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96cbac76537935d0abeb6fd2c22165d632feccbfd98ee96a8f1d59aa743facd1 0.600000000000 1420266 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": 960689, "vin": [ { "gen": { "height": 960679 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96cbac76537935d0abeb6fd2c22165d632feccbfd98ee96a8f1d59aa743facd1" } } ], "extra": [ 1, 92, 195, 59, 14, 73, 191, 79, 180, 32, 83, 215, 200, 78, 42, 143, 234, 227, 59, 137, 19, 99, 110, 239, 191, 237, 242, 8, 67, 213, 217, 39, 1, 2, 17, 0, 0, 0, 3, 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