Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3680aff7f7fa22df3d8b2d962f2b39e4a610bee5d2bb8d791de81a709e7f4dc2

Tx prefix hash: 914ab8334cfedc65ba6a10995d09618c38a55fba1dedaff83d8076ed88061368
Tx public key: b375533b0d5c191a852c135d1fcfcdfc70159e481cbc7db255522ab88baf63cf
Timestamp: 1708015060 Timestamp [UCT]: 2024-02-15 16:37:40 Age [y:d:h:m:s]: 01:262:14:55:31
Block: 958186 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 446453 RingCT/type: yes/0
Extra: 01b375533b0d5c191a852c135d1fcfcdfc70159e481cbc7db255522ab88baf63cf0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 523ea5c6c65ec8fa199a606ce8d373e85a0f34323653dd30f41c3a33ca7a288f 0.600000000000 1417543 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": 958196, "vin": [ { "gen": { "height": 958186 } } ], "vout": [ { "amount": 600000000, "target": { "key": "523ea5c6c65ec8fa199a606ce8d373e85a0f34323653dd30f41c3a33ca7a288f" } } ], "extra": [ 1, 179, 117, 83, 59, 13, 92, 25, 26, 133, 44, 19, 93, 31, 207, 205, 252, 112, 21, 158, 72, 28, 188, 125, 178, 85, 82, 42, 184, 139, 175, 99, 207, 2, 17, 0, 0, 0, 2, 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