Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39fc180c0cd1f27b944ee68ac44cde7620ff8200441ed4e590efba8dc70b3a31

Tx prefix hash: 2e0c4c74ac1cdfa9e622b3407a8b676a5d08226667da074a1bc634dc82db2d3d
Tx public key: e61d2527d2740f0def69b881560e97d3cdccb75a5c073bf550f8ebc78bb647f3
Timestamp: 1730983968 Timestamp [UCT]: 2024-11-07 12:52:48 Age [y:d:h:m:s]: 00:076:06:10:39
Block: 1148532 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54511 RingCT/type: yes/0
Extra: 01e61d2527d2740f0def69b881560e97d3cdccb75a5c073bf550f8ebc78bb647f30211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3991fdb4ff852ed2f21d02cae5b70d18e4c60257ba4d6404f54307a88ab9bb0a 0.600000000000 1633403 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": 1148542, "vin": [ { "gen": { "height": 1148532 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3991fdb4ff852ed2f21d02cae5b70d18e4c60257ba4d6404f54307a88ab9bb0a" } } ], "extra": [ 1, 230, 29, 37, 39, 210, 116, 15, 13, 239, 105, 184, 129, 86, 14, 151, 211, 205, 204, 183, 90, 92, 7, 59, 245, 80, 248, 235, 199, 139, 182, 71, 243, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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