Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87ace31d262753dc1f5f7d9bb9e52829a1b7cfc1b4d76acc86f709e0484c7a55

Tx prefix hash: 6042b0232f69ebfad55c3906d092021286445177355551822fac2a1dfa30a6fd
Tx public key: 6a1a4479297bd627aa654539a0a6fe71092a4ae571f55b3bdac74097849b374f
Timestamp: 1735488378 Timestamp [UCT]: 2024-12-29 16:06:18 Age [y:d:h:m:s]: 00:133:07:36:36
Block: 1185827 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95096 RingCT/type: yes/0
Extra: 016a1a4479297bd627aa654539a0a6fe71092a4ae571f55b3bdac74097849b374f02110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a03ef0add7673c613b6e3f1c6e7ec26f9783beeb71f51d21664536523163b41 0.600000000000 1672302 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": 1185837, "vin": [ { "gen": { "height": 1185827 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a03ef0add7673c613b6e3f1c6e7ec26f9783beeb71f51d21664536523163b41" } } ], "extra": [ 1, 106, 26, 68, 121, 41, 123, 214, 39, 170, 101, 69, 57, 160, 166, 254, 113, 9, 42, 74, 229, 113, 245, 91, 59, 218, 199, 64, 151, 132, 155, 55, 79, 2, 17, 0, 0, 0, 10, 31, 10, 83, 235, 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