Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd9bc5bb6f5c4713b614fed6210609bb640dfb77ef4338d0a89f55dedd291b26

Tx prefix hash: 013c815044aec917dfeae41b59e5f77cd29155327497fe7ffbb27ec2b4d25af1
Tx public key: ae463ca5eacdc9a9bdbc5bb08a4e6b41efbaa182fab5b73010cda056296f9c56
Timestamp: 1734176700 Timestamp [UCT]: 2024-12-14 11:45:00 Age [y:d:h:m:s]: 00:327:00:00:16
Block: 1174995 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231180 RingCT/type: yes/0
Extra: 01ae463ca5eacdc9a9bdbc5bb08a4e6b41efbaa182fab5b73010cda056296f9c560211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b2220bb97bdda5e6b0d6470c7ae9898fa7700810820287a6a2f648a9ac003d4 0.600000000000 1661216 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": 1175005, "vin": [ { "gen": { "height": 1174995 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b2220bb97bdda5e6b0d6470c7ae9898fa7700810820287a6a2f648a9ac003d4" } } ], "extra": [ 1, 174, 70, 60, 165, 234, 205, 201, 169, 189, 188, 91, 176, 138, 78, 107, 65, 239, 186, 161, 130, 250, 181, 183, 48, 16, 205, 160, 86, 41, 111, 156, 86, 2, 17, 0, 0, 0, 2, 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