Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23f6b9c45aaf51bf0195165bc290f3900dc51628fd964512b827940ecdce8868

Tx prefix hash: 7ecf01585b8bf5f188c60199de0e61c9c567e6176782019200fea5b8de03ce27
Tx public key: a339fd318eeecf01cb1f92f643061aa06e4b8caa86e0d79b269d94909de25aec
Timestamp: 1736455119 Timestamp [UCT]: 2025-01-09 20:38:39 Age [y:d:h:m:s]: 00:067:16:57:55
Block: 1193835 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48184 RingCT/type: yes/0
Extra: 01a339fd318eeecf01cb1f92f643061aa06e4b8caa86e0d79b269d94909de25aec0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eceb7377664a5bdd84c0647d6be903f852f681c943ad761e9bbcd1d6435efa53 0.600000000000 1680400 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": 1193845, "vin": [ { "gen": { "height": 1193835 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eceb7377664a5bdd84c0647d6be903f852f681c943ad761e9bbcd1d6435efa53" } } ], "extra": [ 1, 163, 57, 253, 49, 142, 238, 207, 1, 203, 31, 146, 246, 67, 6, 26, 160, 110, 75, 140, 170, 134, 224, 215, 155, 38, 157, 148, 144, 157, 226, 90, 236, 2, 17, 0, 0, 0, 3, 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