Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e93911b4a44072ccc981ac4e8a435e15a379d4aa6eb53a93cfdf376edc6712f5

Tx prefix hash: 96c58343a88ec04e46887407a995adadd7630cb16fd951ea25ee507e913de992
Tx public key: 9c17d4c9c54298c370050f0a4e843442d961f789e8f2aaa6bf5d82bd8a957125
Timestamp: 1726603691 Timestamp [UCT]: 2024-09-17 20:08:11 Age [y:d:h:m:s]: 00:209:10:45:07
Block: 1112303 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149521 RingCT/type: yes/0
Extra: 019c17d4c9c54298c370050f0a4e843442d961f789e8f2aaa6bf5d82bd8a957125021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c6ef6d1b644f9687d880090d81b41e1a2e3b481777ac9057ade5a91e27fb31e 0.600000000000 1591574 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": 1112313, "vin": [ { "gen": { "height": 1112303 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c6ef6d1b644f9687d880090d81b41e1a2e3b481777ac9057ade5a91e27fb31e" } } ], "extra": [ 1, 156, 23, 212, 201, 197, 66, 152, 195, 112, 5, 15, 10, 78, 132, 52, 66, 217, 97, 247, 137, 232, 242, 170, 166, 191, 93, 130, 189, 138, 149, 113, 37, 2, 17, 0, 0, 0, 5, 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