Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ea00116bd46d2af98a32b97c8ed4244be1ba20ebb8cf8fbd2d2947e485e3f38

Tx prefix hash: 592762af4a7d749cd3b5e85fbc35bfbcbcb3792d695c135405d75206085ac801
Tx public key: 9d32caa653aa5b4628a4ef4d17d48f707a5888f4b6e987f65e20ca410d2746f1
Timestamp: 1714485810 Timestamp [UCT]: 2024-04-30 14:03:30 Age [y:d:h:m:s]: 01:191:21:28:30
Block: 1011839 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395775 RingCT/type: yes/0
Extra: 019d32caa653aa5b4628a4ef4d17d48f707a5888f4b6e987f65e20ca410d2746f10211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 098595ab11fa9ac40fc2aaa40b8e9d857670acc165285bcd673adb19b364bdbd 0.600000000000 1474179 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": 1011849, "vin": [ { "gen": { "height": 1011839 } } ], "vout": [ { "amount": 600000000, "target": { "key": "098595ab11fa9ac40fc2aaa40b8e9d857670acc165285bcd673adb19b364bdbd" } } ], "extra": [ 1, 157, 50, 202, 166, 83, 170, 91, 70, 40, 164, 239, 77, 23, 212, 143, 112, 122, 88, 136, 244, 182, 233, 135, 246, 94, 32, 202, 65, 13, 39, 70, 241, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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