Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 123a4acc2c903fd6c7d2bbcf44ba26e1f01690efbc39d3011dd243caa0ce8f18

Tx prefix hash: 83154f6ac1d3f20c32ae9fb65c2a6fb8438a3403dba18db93e7560981f078e6f
Tx public key: 5d85dee696dfb8f7b3650d3b242d5b8e6017c230bee431f84e6e00405f10fc87
Timestamp: 1734415270 Timestamp [UCT]: 2024-12-17 06:01:10 Age [y:d:h:m:s]: 00:092:16:10:27
Block: 1176969 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66026 RingCT/type: yes/0
Extra: 015d85dee696dfb8f7b3650d3b242d5b8e6017c230bee431f84e6e00405f10fc870211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1cf99a5c43d13e93096c8ef09ea0a6fb07cafddb8ada4f89438296741acac631 0.600000000000 1663330 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": 1176979, "vin": [ { "gen": { "height": 1176969 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1cf99a5c43d13e93096c8ef09ea0a6fb07cafddb8ada4f89438296741acac631" } } ], "extra": [ 1, 93, 133, 222, 230, 150, 223, 184, 247, 179, 101, 13, 59, 36, 45, 91, 142, 96, 23, 194, 48, 190, 228, 49, 248, 78, 110, 0, 64, 95, 16, 252, 135, 2, 17, 0, 0, 0, 5, 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