Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e35c63bd0a9b3934ddbef73dd066d529752b3bc114ef2a1d412a76657a076dd

Tx prefix hash: 70d179e293c32462231c15314a6b78a247e2dcef4daf82737d558e5a106bffb0
Tx public key: f75bd1ac97f8ba26d1d97603561d8277e07d5053e8bbd5e1b088b8c0a3ad4692
Timestamp: 1743869900 Timestamp [UCT]: 2025-04-05 16:18:20 Age [y:d:h:m:s]: 00:275:07:27:00
Block: 1254953 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194581 RingCT/type: yes/0
Extra: 01f75bd1ac97f8ba26d1d97603561d8277e07d5053e8bbd5e1b088b8c0a3ad4692021100000007dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35081c175f7c91ff2178bf0b38aac1047a05118afce91e125cb816d32a4bb310 0.600000000000 1742048 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": 1254963, "vin": [ { "gen": { "height": 1254953 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35081c175f7c91ff2178bf0b38aac1047a05118afce91e125cb816d32a4bb310" } } ], "extra": [ 1, 247, 91, 209, 172, 151, 248, 186, 38, 209, 217, 118, 3, 86, 29, 130, 119, 224, 125, 80, 83, 232, 187, 213, 225, 176, 136, 184, 192, 163, 173, 70, 146, 2, 17, 0, 0, 0, 7, 219, 181, 113, 193, 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