Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f540fbeb7727c712875fc682b0c13c34e914cd8823b3d7f60c70044b701a1763

Tx prefix hash: fe4ff7a33d5dd78a0583abe746f0a9d17bb4a86e3110aae5b836e6b8af3c9801
Tx public key: 198bd5937d3f04dbbfc16181a3dc209a9bca9f21bc2dd57b689b34544769ffab
Timestamp: 1702258964 Timestamp [UCT]: 2023-12-11 01:42:44 Age [y:d:h:m:s]: 01:041:11:16:39
Block: 910479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290950 RingCT/type: yes/0
Extra: 01198bd5937d3f04dbbfc16181a3dc209a9bca9f21bc2dd57b689b34544769ffab02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4570a6e80f8d3962e8ff06d2bee66e12979bdd50fa3fbaa403eaac106ccecc44 0.600000000000 1367638 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": 910489, "vin": [ { "gen": { "height": 910479 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4570a6e80f8d3962e8ff06d2bee66e12979bdd50fa3fbaa403eaac106ccecc44" } } ], "extra": [ 1, 25, 139, 213, 147, 125, 63, 4, 219, 191, 193, 97, 129, 163, 220, 32, 154, 155, 202, 159, 33, 188, 45, 213, 123, 104, 155, 52, 84, 71, 105, 255, 171, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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