Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17ebce318086a79e6a3a10d61a431d35de6cddc152e0f4bdd1f6cfc8f060f825

Tx prefix hash: 74a4fd31330310ffc48b59e00ca1eb363ec5fa7522a1b14a6933816c657a64a8
Tx public key: 63fe1edddafcfbb0cf052104d99a6c4d80b1ce90d289ecc2f784e9af56b7f150
Timestamp: 1735315247 Timestamp [UCT]: 2024-12-27 16:00:47 Age [y:d:h:m:s]: 00:102:22:44:53
Block: 1184391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73376 RingCT/type: yes/0
Extra: 0163fe1edddafcfbb0cf052104d99a6c4d80b1ce90d289ecc2f784e9af56b7f150021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b7c31896c2addf6d96adc9acc2af4c6cab313a0d1d110b9acfbbe944745f3ac 0.600000000000 1670848 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": 1184401, "vin": [ { "gen": { "height": 1184391 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b7c31896c2addf6d96adc9acc2af4c6cab313a0d1d110b9acfbbe944745f3ac" } } ], "extra": [ 1, 99, 254, 30, 221, 218, 252, 251, 176, 207, 5, 33, 4, 217, 154, 108, 77, 128, 177, 206, 144, 210, 137, 236, 194, 247, 132, 233, 175, 86, 183, 241, 80, 2, 17, 0, 0, 0, 6, 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