Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae3cf4bd1f18ca81088b5294ba35c7a6c486a8d2f740e4e195acbff753991a43

Tx prefix hash: 594f4a721c225f75296451feca4453a8043c756ea3abf5227ca9c4e7e9e46947
Tx public key: b4c81be8058db977a09341c3ef422f28c1695b6f72ab7859e6ceb149c53ba6a8
Timestamp: 1722153655 Timestamp [UCT]: 2024-07-28 08:00:55 Age [y:d:h:m:s]: 01:103:07:50:47
Block: 1075409 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332338 RingCT/type: yes/0
Extra: 01b4c81be8058db977a09341c3ef422f28c1695b6f72ab7859e6ceb149c53ba6a802110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 905bff00077cd02f71a335e4f5379c696c4c0759fab5a4fcc112d4724dfaccc7 0.600000000000 1547934 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": 1075419, "vin": [ { "gen": { "height": 1075409 } } ], "vout": [ { "amount": 600000000, "target": { "key": "905bff00077cd02f71a335e4f5379c696c4c0759fab5a4fcc112d4724dfaccc7" } } ], "extra": [ 1, 180, 200, 27, 232, 5, 141, 185, 119, 160, 147, 65, 195, 239, 66, 47, 40, 193, 105, 91, 111, 114, 171, 120, 89, 230, 206, 177, 73, 197, 59, 166, 168, 2, 17, 0, 0, 0, 2, 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