Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50e849a429560b5a5d96fcd1749dc9b30801e6e2403405ed2478198ba6f50e54

Tx prefix hash: f64f9441025d425e3b2cb10667a83d4f50ff31e812f798821fc138055aea8860
Tx public key: 95622f3b8bd14119e39f28fa25b74fe1cd6d43afe9da79fa6a82282aeaca3a94
Timestamp: 1705792523 Timestamp [UCT]: 2024-01-20 23:15:23 Age [y:d:h:m:s]: 01:073:21:50:45
Block: 939736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313922 RingCT/type: yes/0
Extra: 0195622f3b8bd14119e39f28fa25b74fe1cd6d43afe9da79fa6a82282aeaca3a9402110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3a60ec21487abc7fcf59a036de9b56aa9295a3c6ee7935c527f90045c4f88d5 0.600000000000 1397852 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": 939746, "vin": [ { "gen": { "height": 939736 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3a60ec21487abc7fcf59a036de9b56aa9295a3c6ee7935c527f90045c4f88d5" } } ], "extra": [ 1, 149, 98, 47, 59, 139, 209, 65, 25, 227, 159, 40, 250, 37, 183, 79, 225, 205, 109, 67, 175, 233, 218, 121, 250, 106, 130, 40, 42, 234, 202, 58, 148, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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