Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b52beea10ff63c90423d9f22da03b71eff5017917b6f6c8d23cc6e5b63e623d5

Tx prefix hash: f4a72b23649fbe5edb9c79a7ac6ea2aa1d9fd7049fb43e70552a7fe6f0621eab
Tx public key: 07e7236b2f0d3c385718c8ffbac6f72e62bb9433e59628218ddcfd634707be11
Timestamp: 1743101546 Timestamp [UCT]: 2025-03-27 18:52:26 Age [y:d:h:m:s]: 00:235:02:32:46
Block: 1248581 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165778 RingCT/type: yes/0
Extra: 0107e7236b2f0d3c385718c8ffbac6f72e62bb9433e59628218ddcfd634707be11021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a374cdcac067c16bd7c9551202bb572036a92d60e87bffe916c31c7f0f7b552d 0.600000000000 1735614 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": 1248591, "vin": [ { "gen": { "height": 1248581 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a374cdcac067c16bd7c9551202bb572036a92d60e87bffe916c31c7f0f7b552d" } } ], "extra": [ 1, 7, 231, 35, 107, 47, 13, 60, 56, 87, 24, 200, 255, 186, 198, 247, 46, 98, 187, 148, 51, 229, 150, 40, 33, 141, 220, 253, 99, 71, 7, 190, 17, 2, 17, 0, 0, 0, 1, 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