Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2ec0ee481eaa4ae7c54ac96337ee1b3bb80f04af132c4b2a401ae0a6eaf35d9

Tx prefix hash: 1542242d6608d31082727d57a20dae04d970101c31c560d0ab8d515f474c1a40
Tx public key: cf863f5cf0461d7041571ce9e6ee146f90209acdcef60a96eb7e5d36253c89df
Timestamp: 1722280744 Timestamp [UCT]: 2024-07-29 19:19:04 Age [y:d:h:m:s]: 00:322:15:59:30
Block: 1076458 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230462 RingCT/type: yes/0
Extra: 01cf863f5cf0461d7041571ce9e6ee146f90209acdcef60a96eb7e5d36253c89df02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ccfdfe55154b306ab5f750fcfacc895bc959b9ece59907c42818c1e71d9d79a1 0.600000000000 1548995 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": 1076468, "vin": [ { "gen": { "height": 1076458 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ccfdfe55154b306ab5f750fcfacc895bc959b9ece59907c42818c1e71d9d79a1" } } ], "extra": [ 1, 207, 134, 63, 92, 240, 70, 29, 112, 65, 87, 28, 233, 230, 238, 20, 111, 144, 32, 154, 205, 206, 246, 10, 150, 235, 126, 93, 54, 37, 60, 137, 223, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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