Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df2ef34494af85915b1479f342eb21098aa953a2e9d607d397257c96b4ac1c7c

Tx prefix hash: 5d2ea4086d8b71d1b5194acbede0e65090d5690ddadd6105353a6e7d00514cc2
Tx public key: dbf236a7027a8f0d6d3642e2558ca787f6b4bfadbeb4114dc3a77557c5f5d95a
Timestamp: 1719132773 Timestamp [UCT]: 2024-06-23 08:52:53 Age [y:d:h:m:s]: 00:278:08:21:43
Block: 1050350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198911 RingCT/type: yes/0
Extra: 01dbf236a7027a8f0d6d3642e2558ca787f6b4bfadbeb4114dc3a77557c5f5d95a02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45c9ee53dca9044ce58593b7074a205cdd32def2ade78d717468140a91a44e23 0.600000000000 1520515 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": 1050360, "vin": [ { "gen": { "height": 1050350 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45c9ee53dca9044ce58593b7074a205cdd32def2ade78d717468140a91a44e23" } } ], "extra": [ 1, 219, 242, 54, 167, 2, 122, 143, 13, 109, 54, 66, 226, 85, 140, 167, 135, 246, 180, 191, 173, 190, 180, 17, 77, 195, 167, 117, 87, 197, 245, 217, 90, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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