Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7210a75314af77e3894b5b6cf3264dd13ddc9667faba1dddf9e53875c15c125f

Tx prefix hash: 274d016978820126f96a900e6739099bc344a2df89dd92c21c9c46660dbea62e
Tx public key: 9ce486e9c8e9cb91fa58ebc971e592042f0812c3e2d3658f82a9ca1bbf0b9e21
Timestamp: 1721464890 Timestamp [UCT]: 2024-07-20 08:41:30 Age [y:d:h:m:s]: 01:080:00:05:32
Block: 1069697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315632 RingCT/type: yes/0
Extra: 019ce486e9c8e9cb91fa58ebc971e592042f0812c3e2d3658f82a9ca1bbf0b9e21021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 447122fdd34b51b57e2345e86aa0da92af7ecd54ff23267bcab3839d9e5a65fb 0.600000000000 1541230 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": 1069707, "vin": [ { "gen": { "height": 1069697 } } ], "vout": [ { "amount": 600000000, "target": { "key": "447122fdd34b51b57e2345e86aa0da92af7ecd54ff23267bcab3839d9e5a65fb" } } ], "extra": [ 1, 156, 228, 134, 233, 200, 233, 203, 145, 250, 88, 235, 201, 113, 229, 146, 4, 47, 8, 18, 195, 226, 211, 101, 143, 130, 169, 202, 27, 191, 11, 158, 33, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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