Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be70943f67b38c57dc0dcfc530aba107ee317801c902b8e288716c8bdd701817

Tx prefix hash: 888a215004609a0dba7a93e54e1040b2c0f87e6bb207f77da183be0256498125
Tx public key: b73efbb33a68b759a79b967e0db56ff1b2d4edc174b49f8f65154c162653177a
Timestamp: 1744916152 Timestamp [UCT]: 2025-04-17 18:55:52 Age [y:d:h:m:s]: 00:019:02:04:53
Block: 1263600 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13667 RingCT/type: yes/0
Extra: 01b73efbb33a68b759a79b967e0db56ff1b2d4edc174b49f8f65154c162653177a021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 353b8574a17df8f42d8b93c8ad27b11c5f6d00cc84c3166c03565db5eace541e 0.600000000000 1750791 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": 1263610, "vin": [ { "gen": { "height": 1263600 } } ], "vout": [ { "amount": 600000000, "target": { "key": "353b8574a17df8f42d8b93c8ad27b11c5f6d00cc84c3166c03565db5eace541e" } } ], "extra": [ 1, 183, 62, 251, 179, 58, 104, 183, 89, 167, 155, 150, 126, 13, 181, 111, 241, 178, 212, 237, 193, 116, 180, 159, 143, 101, 21, 76, 22, 38, 83, 23, 122, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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