Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e65e764f6042a62ccc32da34a587766fc8229a1e56d009618a56c846820d6d6

Tx prefix hash: 050c96be1b4883381bfabe524f57f657a4fe9c8fcadb40780ce028b1e209cfb9
Tx public key: cfd706baa7e9ce9448dab7ef824d0ce6f4229ebb06fb2856cde49d4978d54eb9
Timestamp: 1720407877 Timestamp [UCT]: 2024-07-08 03:04:37 Age [y:d:h:m:s]: 00:311:05:06:50
Block: 1060939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222387 RingCT/type: yes/0
Extra: 01cfd706baa7e9ce9448dab7ef824d0ce6f4229ebb06fb2856cde49d4978d54eb902110000000fe914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02bbfdfe3cb2be0a1e81f16bb6d715470cbaf207d778346b6af5d6655916c4d9 0.600000000000 1531428 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": 1060949, "vin": [ { "gen": { "height": 1060939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02bbfdfe3cb2be0a1e81f16bb6d715470cbaf207d778346b6af5d6655916c4d9" } } ], "extra": [ 1, 207, 215, 6, 186, 167, 233, 206, 148, 72, 218, 183, 239, 130, 77, 12, 230, 244, 34, 158, 187, 6, 251, 40, 86, 205, 228, 157, 73, 120, 213, 78, 185, 2, 17, 0, 0, 0, 15, 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