Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c511a9069c9d9501641b749387a3ea88a82914bbc3eaad71eb84eaca051d0e6

Tx prefix hash: 851c85fa17c37b1c993ba88d5a2b67c014a74a2f9240664c50f64f57e4c20021
Tx public key: 1f10553a6bbd177eb8800dd640d2c841e682b864e37e422860d5a56836531b20
Timestamp: 1711650165 Timestamp [UCT]: 2024-03-28 18:22:45 Age [y:d:h:m:s]: 01:039:02:29:39
Block: 988350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288913 RingCT/type: yes/0
Extra: 011f10553a6bbd177eb8800dd640d2c841e682b864e37e422860d5a56836531b2002110000000159dad3f5000000000000000000

1 output(s) for total of 0.605780000000 dcy

stealth address amount amount idx
00: cb11669981e086b7f3d14836407023646d0aeaaef2d622081ccb049a0d3c5c1f 0.605780000000 1448625 of 0

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": 988360, "vin": [ { "gen": { "height": 988350 } } ], "vout": [ { "amount": 605780000, "target": { "key": "cb11669981e086b7f3d14836407023646d0aeaaef2d622081ccb049a0d3c5c1f" } } ], "extra": [ 1, 31, 16, 85, 58, 107, 189, 23, 126, 184, 128, 13, 214, 64, 210, 200, 65, 230, 130, 184, 100, 227, 126, 66, 40, 96, 213, 165, 104, 54, 83, 27, 32, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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