Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1609d74aa89228d509dea6c11cd51c4f7071b3a7693306e3f623b3a4fa332729

Tx prefix hash: d4892b61beafbe96b41a6e79debb07fcad93345dbd5c4780b8e4661f76e52948
Tx public key: 78a5dee896351b9e7c28a6ad927e8e0152fd7ed1a895758e5ad5c7b98368316e
Timestamp: 1700812425 Timestamp [UCT]: 2023-11-24 07:53:45 Age [y:d:h:m:s]: 01:193:13:42:45
Block: 898481 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 399563 RingCT/type: yes/0
Extra: 0178a5dee896351b9e7c28a6ad927e8e0152fd7ed1a895758e5ad5c7b98368316e021100000009e6d27f9c000000000000000000

1 output(s) for total of 0.647082203000 dcy

stealth address amount amount idx
00: a8de76bf1e8ad7f8237782d86dfe747f9ea8d20005503680a4cdd16b85615c73 0.647082203000 1354900 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": 898491, "vin": [ { "gen": { "height": 898481 } } ], "vout": [ { "amount": 647082203, "target": { "key": "a8de76bf1e8ad7f8237782d86dfe747f9ea8d20005503680a4cdd16b85615c73" } } ], "extra": [ 1, 120, 165, 222, 232, 150, 53, 27, 158, 124, 40, 166, 173, 146, 126, 142, 1, 82, 253, 126, 209, 168, 149, 117, 142, 90, 213, 199, 185, 131, 104, 49, 110, 2, 17, 0, 0, 0, 9, 230, 210, 127, 156, 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