Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7513ad4d459202d8b5d19b1b8dd3fd6200186ea1289dbd409476acdf55abd792

Tx prefix hash: dd651e6cafac42f3f13218140692a1e64088184cd98fb75b9141af2cd8d05d47
Tx public key: 028497067ab37fbfc97dd84df9364a76df420d6b920177f8a617c4fd03cba9ae
Timestamp: 1738189521 Timestamp [UCT]: 2025-01-29 22:25:21 Age [y:d:h:m:s]: 00:139:15:45:39
Block: 1207932 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99764 RingCT/type: yes/0
Extra: 01028497067ab37fbfc97dd84df9364a76df420d6b920177f8a617c4fd03cba9ae021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1273d9f67335346e58bf03f9a97fe37e4dd61ae9d3bc12d8b35d9e9764995ef2 0.600000000000 1694659 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": 1207942, "vin": [ { "gen": { "height": 1207932 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1273d9f67335346e58bf03f9a97fe37e4dd61ae9d3bc12d8b35d9e9764995ef2" } } ], "extra": [ 1, 2, 132, 151, 6, 122, 179, 127, 191, 201, 125, 216, 77, 249, 54, 74, 118, 223, 66, 13, 107, 146, 1, 119, 248, 166, 23, 196, 253, 3, 203, 169, 174, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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