Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a3c1089feac83d757a5616484356945a638cbd56b3bf657c370e728fa7417f0

Tx prefix hash: 790f2da88cf0dcb5b8da0318b0abf2eb048d7231f5a9b0f9e82e36b6d36fd5aa
Tx public key: 77ec266b210178266b76f71439d7d4ec6fb879183325997a39a0977d90983157
Timestamp: 1699647442 Timestamp [UCT]: 2023-11-10 20:17:22 Age [y:d:h:m:s]: 01:205:17:53:09
Block: 888830 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 408280 RingCT/type: yes/0
Extra: 0177ec266b210178266b76f71439d7d4ec6fb879183325997a39a0977d9098315702110000000375e3f0e9000000000000000000

1 output(s) for total of 0.696525850000 dcy

stealth address amount amount idx
00: 0c679128e58ee16cb7473417e98a724e25b1e67fae89c66d2d5ab334ac1e29d8 0.696525850000 1344789 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": 888840, "vin": [ { "gen": { "height": 888830 } } ], "vout": [ { "amount": 696525850, "target": { "key": "0c679128e58ee16cb7473417e98a724e25b1e67fae89c66d2d5ab334ac1e29d8" } } ], "extra": [ 1, 119, 236, 38, 107, 33, 1, 120, 38, 107, 118, 247, 20, 57, 215, 212, 236, 111, 184, 121, 24, 51, 37, 153, 122, 57, 160, 151, 125, 144, 152, 49, 87, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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