Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ebe4d3faa5f776434d2d2e68428b9e3720ac4792dfdf95db9992d3a76a50dd15

Tx prefix hash: 64c01541de8a38270094468910b263303084d51b14eaea4f686f0df417ea71c3
Tx public key: 407f848ea012b9414d7a40d5ea289e0e401e3f88637c357236a5503588e6fa0e
Timestamp: 1734098574 Timestamp [UCT]: 2024-12-13 14:02:54 Age [y:d:h:m:s]: 00:136:13:25:34
Block: 1174350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97391 RingCT/type: yes/0
Extra: 01407f848ea012b9414d7a40d5ea289e0e401e3f88637c357236a5503588e6fa0e0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7829e5a355993865cfdec30912af847183f95b92b4e4153695c5ad39af94e859 0.600000000000 1660491 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": 1174360, "vin": [ { "gen": { "height": 1174350 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7829e5a355993865cfdec30912af847183f95b92b4e4153695c5ad39af94e859" } } ], "extra": [ 1, 64, 127, 132, 142, 160, 18, 185, 65, 77, 122, 64, 213, 234, 40, 158, 14, 64, 30, 63, 136, 99, 124, 53, 114, 54, 165, 80, 53, 136, 230, 250, 14, 2, 17, 0, 0, 0, 3, 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