Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08a1714fbdef973b62f97b1c9c61254418eaa7880f8f5a53791f42e81be5ee58

Tx prefix hash: d707a0a8e3ca38992f17500e4ae219b448789f28512d2b1e527d597fd88bb145
Tx public key: dd6aa410242c39bf94b2c41d5838a61598d3bf55a4f56b00a9b108b47e9c0562
Timestamp: 1741382497 Timestamp [UCT]: 2025-03-07 21:21:37 Age [y:d:h:m:s]: 00:258:23:58:41
Block: 1234365 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182849 RingCT/type: yes/0
Extra: 01dd6aa410242c39bf94b2c41d5838a61598d3bf55a4f56b00a9b108b47e9c05620211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 083ce1bbb85da845d91ab9e4c9e1977b1cefe193fadbb18361d29cb0188652a0 0.600000000000 1721292 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": 1234375, "vin": [ { "gen": { "height": 1234365 } } ], "vout": [ { "amount": 600000000, "target": { "key": "083ce1bbb85da845d91ab9e4c9e1977b1cefe193fadbb18361d29cb0188652a0" } } ], "extra": [ 1, 221, 106, 164, 16, 36, 44, 57, 191, 148, 178, 196, 29, 88, 56, 166, 21, 152, 211, 191, 85, 164, 245, 107, 0, 169, 177, 8, 180, 126, 156, 5, 98, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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