Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5da9498846b53c7c6c6a0754ba339c8403e2c7f83b05168393b8bcb46d187c80

Tx prefix hash: e982b0865b5e22884bb15d029bf69e5d3fad9d3eff56df1185c7c093bbaf5c30
Tx public key: 719c6026313a1a1269eff0afddc2f5281e862bd5088652a25dffa4a028eec599
Timestamp: 1724030997 Timestamp [UCT]: 2024-08-19 01:29:57 Age [y:d:h:m:s]: 00:065:09:01:42
Block: 1090980 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46793 RingCT/type: yes/0
Extra: 01719c6026313a1a1269eff0afddc2f5281e862bd5088652a25dffa4a028eec599021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8838945f66623d1ad14576ca980bf08d7262ed00b8c510b7d2e6a30d32ae2f44 0.600000000000 1565605 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": 1090990, "vin": [ { "gen": { "height": 1090980 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8838945f66623d1ad14576ca980bf08d7262ed00b8c510b7d2e6a30d32ae2f44" } } ], "extra": [ 1, 113, 156, 96, 38, 49, 58, 26, 18, 105, 239, 240, 175, 221, 194, 245, 40, 30, 134, 43, 213, 8, 134, 82, 162, 93, 255, 164, 160, 40, 238, 197, 153, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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