Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e893e459732520cefea8ab78fc39b264cd249ae5aecf113a7a3845ad721cd62e

Tx prefix hash: 4499055f1f6112622723eef0303a6faa4080079221dd94ec43523027f0f5790a
Tx public key: 7515a0f84d0f337eb1d0a1e4e1017a8c6ff89f82533fc63b1b5840d9e63a9ddf
Timestamp: 1713139791 Timestamp [UCT]: 2024-04-15 00:09:51 Age [y:d:h:m:s]: 00:340:06:25:14
Block: 1000660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243288 RingCT/type: yes/0
Extra: 017515a0f84d0f337eb1d0a1e4e1017a8c6ff89f82533fc63b1b5840d9e63a9ddf0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d60004a177dadb17d11a84f214ded84883207db25b8979c5dbe8a06c2e4992d 0.600000000000 1461158 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": 1000670, "vin": [ { "gen": { "height": 1000660 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d60004a177dadb17d11a84f214ded84883207db25b8979c5dbe8a06c2e4992d" } } ], "extra": [ 1, 117, 21, 160, 248, 77, 15, 51, 126, 177, 208, 161, 228, 225, 1, 122, 140, 111, 248, 159, 130, 83, 63, 198, 59, 27, 88, 64, 217, 230, 58, 157, 223, 2, 17, 0, 0, 0, 3, 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