Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 296feb60daab626c9611c1b784bcc8f2e7b8a5c379c132252519978680de46d4

Tx prefix hash: 21db28cb89bf1859d9254c8b3c2ba8cb93f3eeabf9fe1fc6a4069a689d950034
Tx public key: c23c059857a2a0d6d53c70f40556fd592ccd0f82b03ad1de65b7d50368dcc268
Timestamp: 1748891979 Timestamp [UCT]: 2025-06-02 19:19:39 Age [y:d:h:m:s]: 00:243:22:43:46
Block: 1296537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171961 RingCT/type: yes/0
Extra: 01c23c059857a2a0d6d53c70f40556fd592ccd0f82b03ad1de65b7d50368dcc268021100000007bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3004682fb733a4ac8b5abe8a4474d5c9ff2e85e86807c966cbb64b21f3b1f44 0.600000000000 1784048 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": 1296547, "vin": [ { "gen": { "height": 1296537 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3004682fb733a4ac8b5abe8a4474d5c9ff2e85e86807c966cbb64b21f3b1f44" } } ], "extra": [ 1, 194, 60, 5, 152, 87, 162, 160, 214, 213, 60, 112, 244, 5, 86, 253, 89, 44, 205, 15, 130, 176, 58, 209, 222, 101, 183, 213, 3, 104, 220, 194, 104, 2, 17, 0, 0, 0, 7, 191, 81, 178, 162, 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