Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0d8320c5ffb1ee678c46d3017c5c98f10b6c8e32b33df54e36e39d1cf6eb0b8

Tx prefix hash: d2e6f15344b53fd9c00374686ff9de4c4d07d937e30c49f7d1e726175e60b57e
Tx public key: 536d01ec7888f0384dddf0e268d3de46d07c2e82758947bff1961131daac423a
Timestamp: 1713814889 Timestamp [UCT]: 2024-04-22 19:41:29 Age [y:d:h:m:s]: 00:352:10:52:37
Block: 1006287 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251954 RingCT/type: yes/0
Extra: 01536d01ec7888f0384dddf0e268d3de46d07c2e82758947bff1961131daac423a02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 539af6117c5d622f961be44e486a97ae7a0d438484c87527f652bf2ec350e4e7 0.600000000000 1467257 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": 1006297, "vin": [ { "gen": { "height": 1006287 } } ], "vout": [ { "amount": 600000000, "target": { "key": "539af6117c5d622f961be44e486a97ae7a0d438484c87527f652bf2ec350e4e7" } } ], "extra": [ 1, 83, 109, 1, 236, 120, 136, 240, 56, 77, 221, 240, 226, 104, 211, 222, 70, 208, 124, 46, 130, 117, 137, 71, 191, 241, 150, 17, 49, 218, 172, 66, 58, 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