Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b14dd7000696c7a82569fa9f2c88673dcfa1c74d39bbca7c350eb29b6d9bd68d

Tx prefix hash: fca8e57d6115099e4fd72935b2280fc57bc943f334d6923df95fff744ef6e3eb
Tx public key: 8c85b085de2e31ebc3ecd58b157c7072514bd1e66071c3c0b55b244225d83d61
Timestamp: 1704390760 Timestamp [UCT]: 2024-01-04 17:52:40 Age [y:d:h:m:s]: 01:307:06:38:32
Block: 928154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 478408 RingCT/type: yes/0
Extra: 018c85b085de2e31ebc3ecd58b157c7072514bd1e66071c3c0b55b244225d83d6102110000000279bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b268b57a59c1259e2178b7c895c6eef85a436ad3bb15d52001ec18b6297d743 0.600000000000 1386012 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": 928164, "vin": [ { "gen": { "height": 928154 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b268b57a59c1259e2178b7c895c6eef85a436ad3bb15d52001ec18b6297d743" } } ], "extra": [ 1, 140, 133, 176, 133, 222, 46, 49, 235, 195, 236, 213, 139, 21, 124, 112, 114, 81, 75, 209, 230, 96, 113, 195, 192, 181, 91, 36, 66, 37, 216, 61, 97, 2, 17, 0, 0, 0, 2, 121, 189, 163, 190, 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