Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3997f83945726aafda26f293d32c1d7899c4dea9752c835b9d9d7bf99c74c6b

Tx prefix hash: 9e9153e61a75aab0029c133528a86ed62c9fa5dcd97ad2bf2721a117984b2ff3
Tx public key: ba3e25642faf87fb1e8ef3beb4506e9a470f38ede8cf5c3e3e4927666aa95595
Timestamp: 1731022239 Timestamp [UCT]: 2024-11-07 23:30:39 Age [y:d:h:m:s]: 00:197:05:53:33
Block: 1148850 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140838 RingCT/type: yes/0
Extra: 01ba3e25642faf87fb1e8ef3beb4506e9a470f38ede8cf5c3e3e4927666aa955950211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4902b36c3c16a5de9c768edf8b4161c64808b3593dfab64482737f188dd790d7 0.600000000000 1633791 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": 1148860, "vin": [ { "gen": { "height": 1148850 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4902b36c3c16a5de9c768edf8b4161c64808b3593dfab64482737f188dd790d7" } } ], "extra": [ 1, 186, 62, 37, 100, 47, 175, 135, 251, 30, 142, 243, 190, 180, 80, 110, 154, 71, 15, 56, 237, 232, 207, 92, 62, 62, 73, 39, 102, 106, 169, 85, 149, 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