Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc8d5ed79fe6004f3512e3bd99391405206042f38bbf7d891f6492ecdd611b99

Tx prefix hash: 975b3036c262222b9b9da429551d80d59f28bf065e61feb9b5797cb25aa984cc
Tx public key: 88b9b59c55306900617ad1a1ad2b41c7a140819171e6c369b1d28c6f776c3870
Timestamp: 1715467817 Timestamp [UCT]: 2024-05-11 22:50:17 Age [y:d:h:m:s]: 00:289:06:21:10
Block: 1020010 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206702 RingCT/type: yes/0
Extra: 0188b9b59c55306900617ad1a1ad2b41c7a140819171e6c369b1d28c6f776c387002110000000641ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1dba6c383adb4e7aa479e3e2b8ec7ba4dd82d8a566dc4355fe93d8a9850dd003 0.600000000000 1484069 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": 1020020, "vin": [ { "gen": { "height": 1020010 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1dba6c383adb4e7aa479e3e2b8ec7ba4dd82d8a566dc4355fe93d8a9850dd003" } } ], "extra": [ 1, 136, 185, 181, 156, 85, 48, 105, 0, 97, 122, 209, 161, 173, 43, 65, 199, 161, 64, 129, 145, 113, 230, 195, 105, 177, 210, 140, 111, 119, 108, 56, 112, 2, 17, 0, 0, 0, 6, 65, 238, 28, 155, 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