Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01a9f7efedc8aed47ce715df7b48f285633a2022c93f5744acafbda074d796d0

Tx prefix hash: dd67e8bcc8f70c2d09012c32ccc7a923a1ac874cf8e76a95119764d3863e277c
Tx public key: 5d78092b62f439bc524c681a2d0553f73ba178eb794b8b4436bd436d2e3efa62
Timestamp: 1726995758 Timestamp [UCT]: 2024-09-22 09:02:38 Age [y:d:h:m:s]: 01:016:11:08:54
Block: 1115555 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270116 RingCT/type: yes/0
Extra: 015d78092b62f439bc524c681a2d0553f73ba178eb794b8b4436bd436d2e3efa62021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3760195f5f975a587dcfe129eae9d26fae514c74ef43595e087fd6df8881e812 0.600000000000 1595728 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": 1115565, "vin": [ { "gen": { "height": 1115555 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3760195f5f975a587dcfe129eae9d26fae514c74ef43595e087fd6df8881e812" } } ], "extra": [ 1, 93, 120, 9, 43, 98, 244, 57, 188, 82, 76, 104, 26, 45, 5, 83, 247, 59, 161, 120, 235, 121, 75, 139, 68, 54, 189, 67, 109, 46, 62, 250, 98, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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