Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05bf620201517a96e0fe72430b37b94a1988c6298dc85883134c1543f205352b

Tx prefix hash: 850818aa5c14c04e57f010d7176002172eb041dafdad9d3b865c1dcb1afbf096
Tx public key: 7a7e5c0d8d795387b6efed4b230aaea314265cdfe3d960fb2b96d14b6c3257f5
Timestamp: 1727179953 Timestamp [UCT]: 2024-09-24 12:12:33 Age [y:d:h:m:s]: 00:240:08:29:32
Block: 1117081 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171631 RingCT/type: yes/0
Extra: 017a7e5c0d8d795387b6efed4b230aaea314265cdfe3d960fb2b96d14b6c3257f5021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3fbe909398db70a5a6372613a4120867e16673ceead6c6aed443432141b428e0 0.600000000000 1597788 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": 1117091, "vin": [ { "gen": { "height": 1117081 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3fbe909398db70a5a6372613a4120867e16673ceead6c6aed443432141b428e0" } } ], "extra": [ 1, 122, 126, 92, 13, 141, 121, 83, 135, 182, 239, 237, 75, 35, 10, 174, 163, 20, 38, 92, 223, 227, 217, 96, 251, 43, 150, 209, 75, 108, 50, 87, 245, 2, 17, 0, 0, 0, 4, 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