Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd8f2e3b0979cc59283306f11a1b22736ff895a8fec51e5daef0fc2d4174f62b

Tx prefix hash: ddd370d543c6f7d2d90b3b767b4f0b92de5a87ff0833ff86172313745a07f73e
Tx public key: 24f4211d07838200c5bc48dcad8708c162570623e59b1409836148b8e3eb0028
Timestamp: 1695531144 Timestamp [UCT]: 2023-09-24 04:52:24 Age [y:d:h:m:s]: 01:125:19:20:30
Block: 854898 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351015 RingCT/type: yes/0
Extra: 0124f4211d07838200c5bc48dcad8708c162570623e59b1409836148b8e3eb0028021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.902335597000 dcy

stealth address amount amount idx
00: d05ac47305216cbf03f9a898cd0a5f2018d449b2dc68db9d9644316b4f9e9cc7 0.902335597000 1308892 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": 854908, "vin": [ { "gen": { "height": 854898 } } ], "vout": [ { "amount": 902335597, "target": { "key": "d05ac47305216cbf03f9a898cd0a5f2018d449b2dc68db9d9644316b4f9e9cc7" } } ], "extra": [ 1, 36, 244, 33, 29, 7, 131, 130, 0, 197, 188, 72, 220, 173, 135, 8, 193, 98, 87, 6, 35, 229, 155, 20, 9, 131, 97, 72, 184, 227, 235, 0, 40, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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