Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3af1affa74d08438d76a842336dc0f224859d05cccac6a005c006dfc9e4ecc1c

Tx prefix hash: 6391316e84b993c4475e5427c6a852418e68e312f3e401a85d0cf4cf65d16510
Tx public key: 93e7fcb1f0a84faee33da32d486a22e4dbaa71c29125bd6cb03acd0b1af3acb7
Timestamp: 1733611345 Timestamp [UCT]: 2024-12-07 22:42:25 Age [y:d:h:m:s]: 00:333:13:00:08
Block: 1170306 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235869 RingCT/type: yes/0
Extra: 0193e7fcb1f0a84faee33da32d486a22e4dbaa71c29125bd6cb03acd0b1af3acb70211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0443d418ce8870412b6f90ee1fec815014951a67c2a3fe0117de0f8a36d10fd 0.600000000000 1656035 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": 1170316, "vin": [ { "gen": { "height": 1170306 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0443d418ce8870412b6f90ee1fec815014951a67c2a3fe0117de0f8a36d10fd" } } ], "extra": [ 1, 147, 231, 252, 177, 240, 168, 79, 174, 227, 61, 163, 45, 72, 106, 34, 228, 219, 170, 113, 194, 145, 37, 189, 108, 176, 58, 205, 11, 26, 243, 172, 183, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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