Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a29fa8c2719baea952f7c467fa6e1c309959e606aa5e8138b3c740dd4c1124b

Tx prefix hash: 7046812c9879face13fac78ca944f57ec4f4f1085ba1f33692c2f262b2609f8f
Tx public key: 25d3f0625fa9acd4e986d77d6e3e580478b818fa0d66d819bd121fc5235f829c
Timestamp: 1711892390 Timestamp [UCT]: 2024-03-31 13:39:50 Age [y:d:h:m:s]: 01:035:22:37:07
Block: 990350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286659 RingCT/type: yes/0
Extra: 0125d3f0625fa9acd4e986d77d6e3e580478b818fa0d66d819bd121fc5235f829c02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1aa79082e9c1036766c033ec5c06676f24ad44b4ae76ab90de2314877467058d 0.600000000000 1450672 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": 990360, "vin": [ { "gen": { "height": 990350 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1aa79082e9c1036766c033ec5c06676f24ad44b4ae76ab90de2314877467058d" } } ], "extra": [ 1, 37, 211, 240, 98, 95, 169, 172, 212, 233, 134, 215, 125, 110, 62, 88, 4, 120, 184, 24, 250, 13, 102, 216, 25, 189, 18, 31, 197, 35, 95, 130, 156, 2, 17, 0, 0, 0, 7, 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