Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ce1e750931635e275d767a2a8d2146c7d47420ee67e8c703c60f9f68ad9592a

Tx prefix hash: e70d87435885ce6b119b64871215b9c67ff5622db66714d31e885ad32461a873
Tx public key: 8f1b087b379ee1b3ac229114a3c9d62f4711c31ff6d4f2d792f73d24b525cfc0
Timestamp: 1743821915 Timestamp [UCT]: 2025-04-05 02:58:35 Age [y:d:h:m:s]: 00:222:09:27:29
Block: 1254549 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156678 RingCT/type: yes/0
Extra: 018f1b087b379ee1b3ac229114a3c9d62f4711c31ff6d4f2d792f73d24b525cfc0021100000001a2ed016b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4603adc455e059f520fe4085284ff716d1eeb886fb3013de0b1fd6606628da1 0.600000000000 1741630 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": 1254559, "vin": [ { "gen": { "height": 1254549 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4603adc455e059f520fe4085284ff716d1eeb886fb3013de0b1fd6606628da1" } } ], "extra": [ 1, 143, 27, 8, 123, 55, 158, 225, 179, 172, 34, 145, 20, 163, 201, 214, 47, 71, 17, 195, 31, 246, 212, 242, 215, 146, 247, 61, 36, 181, 37, 207, 192, 2, 17, 0, 0, 0, 1, 162, 237, 1, 107, 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