Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36ebf622a3a729d5b4a71555963aba1c0c90d3b0512505a59cd03c02b135190e

Tx prefix hash: ce4f7863e1a5a6fc23f6bb919f166527e902d266b645101a067ffc4097bd99d1
Tx public key: 39140c005b9147d0a22ef91f008a66e3ca67d35f6b3d1b6c802551301737d969
Timestamp: 1674170457 Timestamp [UCT]: 2023-01-19 23:20:57 Age [y:d:h:m:s]: 02:041:11:45:33
Block: 678468 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 551289 RingCT/type: yes/0
Extra: 0139140c005b9147d0a22ef91f008a66e3ca67d35f6b3d1b6c802551301737d96902110000000375e3f0e9000000000000000000

1 output(s) for total of 3.466999790000 dcy

stealth address amount amount idx
00: 7a4515f604f5a85177d69fa1c495343e32201ff14d834cbee961c99ddcfd2e02 3.466999790000 1120353 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": 678478, "vin": [ { "gen": { "height": 678468 } } ], "vout": [ { "amount": 3466999790, "target": { "key": "7a4515f604f5a85177d69fa1c495343e32201ff14d834cbee961c99ddcfd2e02" } } ], "extra": [ 1, 57, 20, 12, 0, 91, 145, 71, 208, 162, 46, 249, 31, 0, 138, 102, 227, 202, 103, 211, 95, 107, 61, 27, 108, 128, 37, 81, 48, 23, 55, 217, 105, 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