Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a7b9535a1f47e2ad69c53f4334205daedb5e167224631c470bc035fcd4fecef

Tx prefix hash: f0636001b03c2a438a951c76a1e9a80b81fb300039a3651caa4ff0e1afc302e4
Tx public key: b48a3adf7150b6d9817ab5137369ac16f1bb63d0cef9cb86cebb177216d6daaa
Timestamp: 1709151145 Timestamp [UCT]: 2024-02-28 20:12:25 Age [y:d:h:m:s]: 01:309:16:41:00
Block: 967617 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 480142 RingCT/type: yes/0
Extra: 01b48a3adf7150b6d9817ab5137369ac16f1bb63d0cef9cb86cebb177216d6daaa0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 99a49971aee417bd961183f99fa3cc5ca8dd4a999276c838b650be4657b22d03 0.600000000000 1427400 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": 967627, "vin": [ { "gen": { "height": 967617 } } ], "vout": [ { "amount": 600000000, "target": { "key": "99a49971aee417bd961183f99fa3cc5ca8dd4a999276c838b650be4657b22d03" } } ], "extra": [ 1, 180, 138, 58, 223, 113, 80, 182, 217, 129, 122, 181, 19, 115, 105, 172, 22, 241, 187, 99, 208, 206, 249, 203, 134, 206, 187, 23, 114, 22, 214, 218, 170, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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