Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e3ab484e445402ea2ff31b9fe16b1b18684383ae05d1cbe0c278a82e67dcf4e

Tx prefix hash: efd80dbe45a22e0e167c85653d2869b54f01d207c5ea015d7cc1830cfd2ede95
Tx public key: 606d954ca4d7051ed293210f304d8b7c119b9bedfc77d4655097d4e2401f3f37
Timestamp: 1737874509 Timestamp [UCT]: 2025-01-26 06:55:09 Age [y:d:h:m:s]: 00:047:17:53:09
Block: 1205544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33945 RingCT/type: yes/0
Extra: 01606d954ca4d7051ed293210f304d8b7c119b9bedfc77d4655097d4e2401f3f37021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a46c41b7e8be724bca04223f5e4dde024eace1452faa98d4baaa886bffc16523 0.600000000000 1692241 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": 1205554, "vin": [ { "gen": { "height": 1205544 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a46c41b7e8be724bca04223f5e4dde024eace1452faa98d4baaa886bffc16523" } } ], "extra": [ 1, 96, 109, 149, 76, 164, 215, 5, 30, 210, 147, 33, 15, 48, 77, 139, 124, 17, 155, 155, 237, 252, 119, 212, 101, 80, 151, 212, 226, 64, 31, 63, 55, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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