Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc6497b806e2506cbb5783efcaee1d3a41a01e22a0afcf9e02858b7e31e7f0e3

Tx prefix hash: afa54a6ad879c7c67992483042d3aafccfe3688247f0dca04e6f3f9d9c4775b2
Tx public key: 7fa2674aad3fdc468deb255f0fa5696e27185e107e8b6ff44e50b4f634794eed
Timestamp: 1719547277 Timestamp [UCT]: 2024-06-28 04:01:17 Age [y:d:h:m:s]: 01:156:23:17:25
Block: 1053804 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370754 RingCT/type: yes/0
Extra: 017fa2674aad3fdc468deb255f0fa5696e27185e107e8b6ff44e50b4f634794eed0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35edfcaf4b8b67e7fd77986a0fb5f9da07bf9a490d6281acee5f4f2b94d8ee49 0.600000000000 1524155 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": 1053814, "vin": [ { "gen": { "height": 1053804 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35edfcaf4b8b67e7fd77986a0fb5f9da07bf9a490d6281acee5f4f2b94d8ee49" } } ], "extra": [ 1, 127, 162, 103, 74, 173, 63, 220, 70, 141, 235, 37, 95, 15, 165, 105, 110, 39, 24, 94, 16, 126, 139, 111, 244, 78, 80, 180, 246, 52, 121, 78, 237, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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