Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2dbd0d6b66d82f412a55a3238457aed4647d60764e74693734d8b58bad8fe402

Tx prefix hash: ffa865d5f5a508dde10225ae07045b8c2da78a2e83a3caf7562c6f1ba137a4ac
Tx public key: 1721d3a1425b547c2ec6fd3b33ab5b7017ba8eec1ce9ecccfba4bc5f35395360
Timestamp: 1727424913 Timestamp [UCT]: 2024-09-27 08:15:13 Age [y:d:h:m:s]: 00:057:23:37:53
Block: 1119120 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41430 RingCT/type: yes/0
Extra: 011721d3a1425b547c2ec6fd3b33ab5b7017ba8eec1ce9ecccfba4bc5f3539536002110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a631236281fefcd95f16f041889f21d28dc3a248c46ceba947dd1a33e535bd7d 0.600000000000 1600557 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": 1119130, "vin": [ { "gen": { "height": 1119120 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a631236281fefcd95f16f041889f21d28dc3a248c46ceba947dd1a33e535bd7d" } } ], "extra": [ 1, 23, 33, 211, 161, 66, 91, 84, 124, 46, 198, 253, 59, 51, 171, 91, 112, 23, 186, 142, 236, 28, 233, 236, 204, 251, 164, 188, 95, 53, 57, 83, 96, 2, 17, 0, 0, 0, 10, 145, 225, 60, 4, 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