Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db2c5a62a24fa31e99bdfd7dca5b3af749890c7096dff5811a240f69c6e36ea0

Tx prefix hash: 5ba44f69fd12b8339fdc12ae989e520fb01d684e24ccc14fb770b99c019459f0
Tx public key: db42b2d6bcd360bce803e63a8ffd6a1e3659441146047ebbd0ab413797607255
Timestamp: 1712770185 Timestamp [UCT]: 2024-04-10 17:29:45 Age [y:d:h:m:s]: 00:346:17:11:00
Block: 997591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247912 RingCT/type: yes/0
Extra: 01db42b2d6bcd360bce803e63a8ffd6a1e3659441146047ebbd0ab4137976072550211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5c2c31680e2a58117bdd79c104e8ef99d9aa1ae0bfe3676c8f278fd31fd22f3 0.600000000000 1458025 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": 997601, "vin": [ { "gen": { "height": 997591 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5c2c31680e2a58117bdd79c104e8ef99d9aa1ae0bfe3676c8f278fd31fd22f3" } } ], "extra": [ 1, 219, 66, 178, 214, 188, 211, 96, 188, 232, 3, 230, 58, 143, 253, 106, 30, 54, 89, 68, 17, 70, 4, 126, 187, 208, 171, 65, 55, 151, 96, 114, 85, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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