Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3358cd6534d803239cb6ec61b7a54d0a7ec67870caca7d8f33fe54a08391af4f

Tx prefix hash: e79a7e479bd126eec55c9fdb1c0dca3423cf75750143db8fbe8f31cc8099d3f4
Tx public key: 8241ab24bb743b25164d7a283875ec4b48fb9454621d8ae5f1e45a6aff632840
Timestamp: 1703484370 Timestamp [UCT]: 2023-12-25 06:06:10 Age [y:d:h:m:s]: 00:330:03:33:18
Block: 920636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236391 RingCT/type: yes/0
Extra: 018241ab24bb743b25164d7a283875ec4b48fb9454621d8ae5f1e45a6aff63284002110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d04459e5bdf0df531e19a0b7a30b6e4addcdb80fa754bef6349efc9353cbd2a 0.600000000000 1378316 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": 920646, "vin": [ { "gen": { "height": 920636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d04459e5bdf0df531e19a0b7a30b6e4addcdb80fa754bef6349efc9353cbd2a" } } ], "extra": [ 1, 130, 65, 171, 36, 187, 116, 59, 37, 22, 77, 122, 40, 56, 117, 236, 75, 72, 251, 148, 84, 98, 29, 138, 229, 241, 228, 90, 106, 255, 99, 40, 64, 2, 17, 0, 0, 0, 1, 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