Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f80305cc028ce1c493e1b77b7f82f86e2f0335e8767a50e9a3b599d38fd4f416

Tx prefix hash: 945525f2699ded50ed6e8e03194f680bc9ccaf14ff232515c20937f54631542f
Tx public key: 14c5a01f1098eeff3987ce1faa7b4a095c35336d4201fca9982aed0d60562ac4
Timestamp: 1732128100 Timestamp [UCT]: 2024-11-20 18:41:40 Age [y:d:h:m:s]: 00:116:10:21:15
Block: 1158005 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83038 RingCT/type: yes/0
Extra: 0114c5a01f1098eeff3987ce1faa7b4a095c35336d4201fca9982aed0d60562ac40211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 696f621f88488ac9d64e1f2d85321e29315c4acdf65caf46c0e89a15a5251af0 0.600000000000 1643630 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": 1158015, "vin": [ { "gen": { "height": 1158005 } } ], "vout": [ { "amount": 600000000, "target": { "key": "696f621f88488ac9d64e1f2d85321e29315c4acdf65caf46c0e89a15a5251af0" } } ], "extra": [ 1, 20, 197, 160, 31, 16, 152, 238, 255, 57, 135, 206, 31, 170, 123, 74, 9, 92, 53, 51, 109, 66, 1, 252, 169, 152, 42, 237, 13, 96, 86, 42, 196, 2, 17, 0, 0, 0, 9, 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