Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a5aed2fcf6c140e1d3652a2ec88caf178f7ee564f7c34af0ec20afd60e53beb

Tx prefix hash: d18dd90560d758d5f0fa182d676b1f22816d00ad2ab6fb70262eb6f47b938b7a
Tx public key: 8a7b745cfedce521c9eca8ad2a53f3e83d3acb28315d91bdaeb55fa6846878ee
Timestamp: 1717824630 Timestamp [UCT]: 2024-06-08 05:30:30 Age [y:d:h:m:s]: 00:313:23:30:39
Block: 1039524 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224393 RingCT/type: yes/0
Extra: 018a7b745cfedce521c9eca8ad2a53f3e83d3acb28315d91bdaeb55fa6846878ee02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b25b3fa76cd03d6b77f83bf409352c8804cf6231fb79b49c36d20221dca6722 0.600000000000 1508167 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": 1039534, "vin": [ { "gen": { "height": 1039524 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b25b3fa76cd03d6b77f83bf409352c8804cf6231fb79b49c36d20221dca6722" } } ], "extra": [ 1, 138, 123, 116, 92, 254, 220, 229, 33, 201, 236, 168, 173, 42, 83, 243, 232, 61, 58, 203, 40, 49, 93, 145, 189, 174, 181, 95, 166, 132, 104, 120, 238, 2, 17, 0, 0, 0, 3, 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