Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e81b9d55ea54fb8e495df4d0bb87d0287d80c9fbbb5ad548a955dd8959c0664

Tx prefix hash: 9a5deb280cc7cc9fd73d842b020da52b882665a69160dc229a8a4137de9a3fcd
Tx public key: c41673ef98c5e301bb195b5f07c0ccd7723f14b205d27291c70aaee0b1685006
Timestamp: 1725586931 Timestamp [UCT]: 2024-09-06 01:42:11 Age [y:d:h:m:s]: 00:079:12:24:35
Block: 1103881 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56857 RingCT/type: yes/0
Extra: 01c41673ef98c5e301bb195b5f07c0ccd7723f14b205d27291c70aaee0b1685006021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a70388dc8a48469c81a4e3cec763f77c0ed87b69facd07f9a0c53449b16e6a91 0.600000000000 1580878 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": 1103891, "vin": [ { "gen": { "height": 1103881 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a70388dc8a48469c81a4e3cec763f77c0ed87b69facd07f9a0c53449b16e6a91" } } ], "extra": [ 1, 196, 22, 115, 239, 152, 197, 227, 1, 187, 25, 91, 95, 7, 192, 204, 215, 114, 63, 20, 178, 5, 210, 114, 145, 199, 10, 174, 224, 177, 104, 80, 6, 2, 17, 0, 0, 0, 4, 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