Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89f23811290e5e499b8847bf5af67b3775b801ee5ed8cffb393904c4a206718a

Tx prefix hash: 60d6d677a01369d9bd0169e733599c0f85cfd2c2470152a04ac1fe85dcc39a4e
Tx public key: 06d278c8e556ef8b2396b1d10532a8fe7b0ffb55868c090238ca1d6172a69fc2
Timestamp: 1748129478 Timestamp [UCT]: 2025-05-24 23:31:18 Age [y:d:h:m:s]: 00:185:16:08:17
Block: 1290224 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130408 RingCT/type: yes/0
Extra: 0106d278c8e556ef8b2396b1d10532a8fe7b0ffb55868c090238ca1d6172a69fc20211000000019f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7e1828780021f6b5aee0ebf8a5b617015d9dfa1432aea014e88895cdbd22ac5 0.600000000000 1777693 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": 1290234, "vin": [ { "gen": { "height": 1290224 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7e1828780021f6b5aee0ebf8a5b617015d9dfa1432aea014e88895cdbd22ac5" } } ], "extra": [ 1, 6, 210, 120, 200, 229, 86, 239, 139, 35, 150, 177, 209, 5, 50, 168, 254, 123, 15, 251, 85, 134, 140, 9, 2, 56, 202, 29, 97, 114, 166, 159, 194, 2, 17, 0, 0, 0, 1, 159, 159, 230, 140, 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