Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48532bea17b54bee7ad70e9abe7af394437e57b3da12702d91ecb717d93d4d95

Tx prefix hash: 15ca34adb9ddd4ac30231de8cfe3e7f471b01cbe8d981b72d72b15b04b918e25
Tx public key: 4fd0b985c5b3c468bffc4e0d4dea7a6b4b47b51acd84dc8f37d171746494b078
Timestamp: 1721418955 Timestamp [UCT]: 2024-07-19 19:55:55 Age [y:d:h:m:s]: 01:112:04:43:43
Block: 1069349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338658 RingCT/type: yes/0
Extra: 014fd0b985c5b3c468bffc4e0d4dea7a6b4b47b51acd84dc8f37d171746494b078021100000001ddd3db91000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4f483ba99a97a56a1d098b83ec9b44ed39b6e6fffe292a68f359aa908412afb 0.600000000000 1540734 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": 1069359, "vin": [ { "gen": { "height": 1069349 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4f483ba99a97a56a1d098b83ec9b44ed39b6e6fffe292a68f359aa908412afb" } } ], "extra": [ 1, 79, 208, 185, 133, 197, 179, 196, 104, 191, 252, 78, 13, 77, 234, 122, 107, 75, 71, 181, 26, 205, 132, 220, 143, 55, 209, 113, 116, 100, 148, 176, 120, 2, 17, 0, 0, 0, 1, 221, 211, 219, 145, 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