Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ff81b0a4c8384d140ce5910421d0ab725fb0af2c9940c092a97b6e84879c296

Tx prefix hash: 0045d26dda1e7c940a287d94fa801b0bb6ecf91891bdad563d07693e1a29849c
Tx public key: d691e0019294c3932e518e61f848cb96073b7fbad8715ee14e1a040e8de09a3b
Timestamp: 1737656410 Timestamp [UCT]: 2025-01-23 18:20:10 Age [y:d:h:m:s]: 00:149:17:01:03
Block: 1203739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106673 RingCT/type: yes/0
Extra: 01d691e0019294c3932e518e61f848cb96073b7fbad8715ee14e1a040e8de09a3b0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9fb95683af4f23d620be4b1256f62ebe5ac93af332a8d91af551ae4e92901e4 0.600000000000 1690418 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": 1203749, "vin": [ { "gen": { "height": 1203739 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9fb95683af4f23d620be4b1256f62ebe5ac93af332a8d91af551ae4e92901e4" } } ], "extra": [ 1, 214, 145, 224, 1, 146, 148, 195, 147, 46, 81, 142, 97, 248, 72, 203, 150, 7, 59, 127, 186, 216, 113, 94, 225, 78, 26, 4, 14, 141, 224, 154, 59, 2, 17, 0, 0, 0, 4, 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